-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Add MAX32657 NS Board #88706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add MAX32657 NS Board #88706
Conversation
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
@@ -2,4 +2,5 @@ | |||
# SPDX-License-Identifier: Apache-2.0 | |||
|
|||
config BOARD_MAX32657EVKIT | |||
select SOC_MAX32657 if BOARD_MAX32657EVKIT_MAX32657 | |||
select SOC_MAX32657 if BOARD_MAX32657EVKIT_MAX32657 || \ | |||
BOARD_MAX32657EVKIT_MAX32657_NS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix alignment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My local tab size was 4, so missed this one, updated it as 8 and fixed. thanks.
BOARD: max32657evkit/max32657/ns | ||
================================ | ||
|
||
The ``max32657evkit/max32657/ns`` board configuration is used to build the secure firmware |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
board target, no such term as board configuration in zephyr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added to classify them to simplify readability. I can update it if require?
- BOARD: max32657evkit/max32657
- BOARD: max32657evkit/max32657/ns
03b0cb7
to
88f3b8d
Compare
@tomi-font @Vge0rge @valentinkorenblit https://github.com/zephyrproject-rtos/zephyr/actions/runs/14994134092/job/42124527322?pr=88706 |
It's happening (only) on your PR because that PR was merged while #89370 is still waiting for @stephanosio's approval. I'd say either wait for it to be merged, or cherry pick that PR into your PR if you want to see CI results, but anyway in the end the other PR will have to go in first. |
Update tf-m node to get MAX32657 support Signed-off-by: Sadik Ozer <[email protected]>
This commit adds MAX32657 Non-Secure peripheral support Signed-off-by: Sadik Ozer <[email protected]>
Rebased onto main to get #89370 |
:kconfig:option:`CONFIG_TRUSTED_EXECUTION_SECURE` to ``y`` and | ||
:kconfig:option:`CONFIG_BUILD_WITH_TFM` to ``n`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Parentheses maybe?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, added.
BOARD: max32657evkit/max32657/ns | ||
================================ | ||
|
||
The ``max32657evkit/max32657/ns`` target is used to build the secure firmware |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, not just board or target. Board target.
The ``max32657evkit/max32657/ns`` target is used to build the secure firmware | |
The ``max32657evkit/max32657/ns`` board target is used to build the secure firmware |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated, thanks.
This commit enables max32657 NS board support To build: - west build -b max32657evkit/max32657/ns -p Signed-off-by: Sadik Ozer <[email protected]>
MAX32657 has one UART interface, It can be used either on TF-M or Zephyr Enabling debug (TFM_SPM_LOG_LEVEL || TFM_PARTITION_LOG_LEVEL) will transfer it to the TF-M side Disabling TF-M debug will transfer it to the Zephyr side. This commit disable TFM debugs Signed-off-by: Sadik Ozer <[email protected]>
This commit provides flashing tfm_merged.hex (includes mcuboot+tfm+ns_image) on default. Signed-off-by: Mert Ekren <[email protected]>
JWT test fails on max32657evkit/max32657/ns board, due to it requries hardware TRNG on TF-M side which not activated yet until it's issue been fixed it is excluded from automated test to workflow been succeeded Signed-off-by: Sadik Ozer <[email protected]>
This commit enables secure_partion sample for max32657evkit NS board Signed-off-by: Sadik Ozer <[email protected]>
This commit enable psa_protected_storage test for max32657evkit/ns board Signed-off-by: Sadik Ozer <[email protected]>
Update psa_crypto test not work on MAX32657 This commit enable/disable flags for MAX32657 to make it works for MAX32657. Signed-off-by: Sadik Ozer <[email protected]>
Set HAL_ADI_PATH to TF-M uses hal_adi that comes with zephyr. Signed-off-by: Sadik Ozer <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functional changes look good. Didn't check the documentation or DT stuff in detail.
|
@nordicjm please revisit. |
FYI I see he's off this week. |
@d3zd3z please review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some minor comment. Not mandatory to address them, but it would be nice to do in case you update the PR for some other reason.
config BUILD_WITH_TFM | ||
default y if TRUSTED_EXECUTION_NONSECURE | ||
help | ||
Auto set WITH_TFM for a Non-Secure version of the board, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auto set WITH_TFM for a Non-Secure version of the board, | |
Auto set BUILD_WITH_TFM for a Non-Secure version of the board. |
/* | ||
* slot1_partition: partition@f0000 { | ||
* label = "image-1"; | ||
* reg = <0xf0000 DT_SIZE_K(0)>; | ||
* }; | ||
* slot1_ns_partition: partition@f0000 { | ||
* label = "image-1-nonsecure"; | ||
* reg = <0xf0000 DT_SIZE_K(0)>; | ||
* }; | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this slot1_
nodes are somehow related to McuBoot update process, but it would be nice to add a short comment which explains why we have some code commented out and when it might be needed to uncomment it. Wdyt?
@@ -8,6 +8,8 @@ common: | |||
- qemu_x86 | |||
extra_configs: | |||
- CONFIG_TEST_RANDOM_GENERATOR=y | |||
platform_exclude: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code change is OK, but there's a typo in the commit message: Exlucde
--> Exclude
.
Add MAX32657 NS board support.
This PR will be enabled after: #88651Blinky Example Output:
